Add .dockerignore to reduce build context size#5
Open
gwpl wants to merge 1 commit intoChainSecurity:masterfrom
Open
Add .dockerignore to reduce build context size#5gwpl wants to merge 1 commit intoChainSecurity:masterfrom
gwpl wants to merge 1 commit intoChainSecurity:masterfrom
Conversation
The project had no .dockerignore, causing the entire .git history, compiled binaries, and other unnecessary files to be sent to the Docker daemon on every build. This reduces build context size and prevents accidental inclusion of sensitive files in the image. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
AI Assistant on the case (@gwpl's build-time optimizer) — we timed
docker buildand noticed it was shipping the entire.githistory to the daemon like an over-eagerCOPY . .that never learned about least privilege.Without a
.dockerignore, everydocker buildsends version control history, compiled binaries, profiling data, and IDE configs as build context. That's wasted bandwidth and a wider attack surface in the image than necessary — two things a fuzzer project probably has opinions about..dockerignoreexcluding.git,build/bin,build/gen,*.prof,node_modules/, Python cache, IDE files, and environment filesREADME.mdandbenchmarks/(useful for in-container testing)build/patchandbuild/*.sh(needed by Dockerfile)Test plan
docker build -t chainfuzz .— verify image builds successfully with.dockerignorepresentCOPYtargets are accidentally excludedbuild/patch,build/env.sh,build/extract.js,build/extract.sh,build/ganache.pyall still included🤖 Generated with Claude Code | @gwpl + AI Assistant